home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: strings.h
- Date: 21 Feb 1996 13:00:00 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4gg14gINNr9o@keats.ugrad.cs.ubc.ca>
- References: <4gao9h$7g2@news.bu.edu> <danpop.824774837@rscernix>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <danpop.824774837@rscernix>, Dan Pop <danpop@mail.cern.ch> wrote:
- >In <4gao9h$7g2@news.bu.edu> lachesis@cs.bu.edu (wai yip) writes:
- >
- >>can anyone who has the header file strings.h please email me and tell me
- >>what is in it or just mail me the header file?
- >
- >I will violate some copyrights and post the version on my system, without
- >omitting a single byte :-)
-
- [ snip ]
-
- > /*
- > * OSF/1 Release 1.0
- > */
- >
- > #include <string.h>
- >
- >That's it. Hope DEC and/or IBM won't sue me :-)
-
- That's pretty funny.
-
- Normally, <strings.h> is supposed to declare certain BSD-specific functions
- that are not part of the C standard. These include things like index() and
- rindex() which are basically identical to the standard strchr() and strrchr(),
- respectively.
-
- On many modern UNIX systems, the declarations are combined into one file, and
- strings.h just includes string.h. Under Linux, the BSD-specific declarations in
- string.h are passed through only if the special switch __USE_BSD is defined.
-
- There is no need to use index() or rindex(), except when you need to compile
- on some old BSD-derived system that predates the standardization.
-
- A lot of socket code traditionally uses bcopy(), bzero() and friends, the idea
- being that these functions are present in any environment where the socket
- calls are.
- --
-
-